Conversation
Full sweep via go get -u ./... after the security-driven bumps. Notable: gocloud.dev 0.39→0.45, sentry-go 0.31→0.46, viper 1.19→1.21, testcontainers 0.36→0.42, gin-contrib/static, miniredis, sprig, otelgrpc/otelhttp contrib, golang-migrate. outpost-go SDK held at v0.4.0 — v1.x is a breaking API change that would require updating cmd/seed; out of scope for a deps refresh.
cmd/seed was the only internal consumer of sdks/outpost-go and held the module on v0.4.0. Replacing with direct HTTP calls removes the dep entirely and unblocks future SDK regenerations.
Refresh after rebase onto main; ~2 weeks of upstream releases since the original bump. Notably pgx v5.9.2 -> v5.10.0 and the aws-sdk-go-v2 set. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
* chore(deps): clear npm security alerts in examples/demos dashboard-integration: next 15.5.2 -> 15.5.19 (+ eslint-config-next), clearing the Next.js RCE critical and 4 highs. Three moderates remain that only have next-16 fixes (one vendored inside next). nodejs: @google-cloud/pubsub v4 -> v5 and swap the abandoned esrun TS runner for tsx. Clears 3 criticals (protobufjs, form-data, fast-xml-parser) and all highs. Two residual transitive otel moderates have no real upstream fix. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore(deps): bump examples/demos to latest Take both demo apps to the latest of every dependency. nodejs: @aws-sdk/client-sqs, amqplib 0.10->2, dotenv 16->17, typescript 5->6, @types/node 22->25, @hookdeck/outpost-sdk 1.0->1.4 (also fixes a stale typecheck error in publish-api.ts). dashboard-integration: next 15->16 (+ eslint-config-next, react 19.2), typescript 5->6, zod/pg/winston/lucide-react etc. Notable migration work: - next 16 defaults to Turbopack, which scoped module resolution to the demo dir and couldn't follow the symlinked @hookdeck/outpost-sdk (file: link to ../../../sdks/outpost-typescript). Set turbopack.root to the repo root so it traverses the link. - Migrate eslint flat config off the FlatCompat/@eslint/eslintrc shim to eslint-config-next 16's native flat exports (the shim throws a circular-config error under config-next 16). Drop @eslint/eslintrc. - eslint kept at ^9: eslint-config-next 16 breaks under eslint 10. - react-hooks/set-state-in-effect (new error in config-next 16) set to warn to match the demo's existing relaxed lint posture. - Fix pre-existing type error: events.list() returns EventPaginatedResult directly (.models), not wrapped in .result. Both apps: build + lint pass. Residual moderate advisories have no real upstream fix (otel core via pubsub; next/next-auth/postcss with no stable patch yet). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
alexbouchardd
approved these changes
Jun 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Most open Dependabot alerts in
go.modhaven't been actioned, including a couple of criticals (pgx memory safety, grpc auth bypass). This brings every direct Go dep up to latest and clears the backlog so future bumps stay incremental instead of multi-year jumps.Docker advisories (Dependabot alerts 407, 408, 409) remain open — no upstream patch, test-only dep via testcontainers.
npm and pip alerts in
sdks/*,website/,internal/portal/, andexamples/are out of scope here; theexamples/demos/*npm alerts are handled in a follow-up PR stacked on this one.